New ArkNEW ARKACOUSTIC DETECTION

BUYER KNOWLEDGE / NEW ARK

New Ark Buyer Questions & Answers

Clear answers for choosing acoustic drone detection, planning a credible pilot and working with New Ark. Explore the company, products, integration and commercial questions that matter to your project.

100 questions found · of 100

01—10

Company & Supplier Credibility

Read topic
01

Who is New Ark, and what does the company actually build?

New Ark is the brand of Hong Kong New Ark Intelligent Technology Limited. Its focus is acoustic drone detection and low-altitude security for oil and gas, chemical, energy and other critical infrastructure. The catalogue includes microphone-array products, acoustic and electro-optical system references, and complementary sensing and integration options.

For a purchase, distinguish a complete detection system from an array, a PCBA delivery or an integration scope. Confirm the selected hardware, processing, interfaces and acceptance criteria in writing; a catalogue listing does not establish every capability for every configuration.

02

Where is New Ark based, and where are your systems manufactured?

New Ark operates as Hong Kong New Ark Intelligent Technology Limited. The Contact page lists Shenzhen project coordination and a Chengdu R&D and system-integration centre, alongside a controlled demonstration-site reference. These help identify the relevant team for a project discussion.

Those locations should not be treated as proof that every proposed unit is manufactured there. Ask the quotation to identify the contracting entity, hardware origin, assembly arrangements and parties responsible for testing and delivery. Local assembly, maintenance and spare-part arrangements can be discussed within the written project scope.

03

How long has New Ark been working on acoustic drone detection?

New Ark's published team statement cites more than 40 years of industry experience for its chief acoustic scientist and an average of more than 20 years for the engineering team. Those figures describe professional experience, not the company's age or the duration of a particular drone-detection product programme.

A founding year and an acoustic-drone-development timeline are not established here. For procurement diligence, request a dated company and product history, separating individual experience, product development milestones and independently verifiable project experience rather than treating them as interchangeable.

04

Is New Ark the same company as Newark Electronics or Newark airport?

No. New Ark, the brand of Hong Kong New Ark Intelligent Technology Limited, is a distinct business from Newark Electronics and element14, and from Newark Liberty Airport. Its stated focus is acoustic drone detection and low-altitude security, not electronic-component distribution or airport operation.

Similar spelling is not evidence of a business relationship. When checking a supplier, use the full legal name and the New Ark contact details, and verify the entity shown on the quotation or contract. No affiliation with those other organisations is asserted.

05

Is New Ark connected to the ARK: Survival game?

No connection to the ARK video games is asserted. New Ark is the brand of Hong Kong New Ark Intelligent Technology Limited, whose business focus is acoustic drone detection and low-altitude security for critical infrastructure. The shared word does not identify the same business or product family.

If you are looking for security equipment, check the company About page and product catalogue rather than game-related search results. For supplier verification, match the full legal name and official contact details to the entity named in your procurement documents.

06

Can you show reference sites we can verify?

A named, independently verifiable reference site is not established here. Ask whether a reference relevant to your industry and proposed configuration can be shared with the site's permission. A useful reference should distinguish the equipment installed, operating environment and functions actually evaluated from broader marketing descriptions.

Where disclosure is restricted, discuss an authorised demonstration or field-validation request through the contact page. Agree on targets, background activity, observation periods and acceptance measures beforehand; a video or demonstration alone should not be treated as proof of performance at your facility.

07

Who leads the acoustics team, and how large is the engineering group?

The published team statement identifies a chief acoustic scientist with more than 40 years of industry experience and an engineering team averaging more than 20 years. It does not establish the scientist's name or the engineering group's headcount, so neither should be inferred from those experience figures.

For your project, request the proposed technical lead's responsibilities and the resources assigned to acoustic assessment, integration and acceptance work. Confirm who answers technical questions and who approves deliverables; relevant assigned capability is more useful than an unsupported total staff number.

08

Do you build your own microphone arrays or resell third-party hardware?

New Ark's catalogue includes the LS8118F and 8026F acoustic arrays, and its PCBA delivery scope supports discussions of microphone-array acquisition, acoustic processing and OEM/ODM integration. These offerings do not, by themselves, establish that every component is manufactured in-house or that no third-party hardware is used.

Request a configuration-specific description of design, sourcing, assembly and testing responsibilities. Where procurement requires origin or ownership information, confirm the relevant BOM, manufacturing arrangements and contractual rights in writing rather than assuming them from the product branding.

09

Which certifications does the company hold?

No specific company certification, including ISO 9001 or ISO 27001, is verified here. Company management-system certification and product conformity are different questions: a certificate for an organisation would not automatically establish compliance or suitability for an individual acoustic array or installation.

If your tender requires certification, request the actual certificate or declaration and check the legal entity, covered scope, applicable standards, issuer and validity. Match product-related documents to the exact model and version offered, and have your procurement or compliance team assess whether they satisfy the requirement.

10

Who owns the data the system collects, and where is it stored?

Data ownership and storage location must be defined for the chosen deployment; neither a customer-ownership rule nor an on-premise or cloud default is established here. Start by identifying whether the configuration collects raw audio, acoustic features, events or identifiers, because these create different data-governance questions.

The project agreement should specify ownership and permitted use, storage locations, retention, access, transfers and deletion responsibilities. Ask how each data type moves between arrays, processing systems and integrations, and have the responsible privacy and security teams review that documented flow before deployment.

11—20

Technology & Project Fit

Read topic
11

Why choose acoustic detection instead of radar or RF?

Acoustic sensing listens for existing motor, rotor and airframe sound rather than transmitting sensing RF. It can therefore contribute observations when a drone has no observable radio-control link, and it does not need visible illumination. Its usefulness still depends on the sound reaching the array above the site's background noise.

The choice is usually about complementary evidence, not replacing every other sensor. Radar, authorised RF reception and EO/IR can corroborate acoustic observations. Compare the combined approach against your targets, industrial noise, obstructions and required outputs through site-specific validation.

12

Can acoustic detection find drones that fly without radio control?

Potentially, yes: motor, rotor and airframe sound may remain observable even when a drone has no radio-control link. Acoustic sensing uses that sound rather than relying on control transmissions. Detection still requires a usable acoustic signal under the actual noise, propagation and obstruction conditions.

Sound alone cannot establish that a drone uses a fibre-optic link, nor does this principle guarantee detection of every autonomous or non-radio-controlled aircraft. Validate the relevant target and flight conditions, and use radar or EO/IR corroboration where appropriate to strengthen the assessment.

13

Does it work at night, in fog, rain or snow?

Acoustic sensing does not require visible illumination, so darkness is not the same limitation it can be for a visible-light camera. That does not establish all-weather performance: wind, precipitation, propagation and obstruction can change the quality of the sound available to an array.

For fog, rain or snow, assess both detection performance and the selected hardware's environmental suitability. Request configuration-specific operating limits and validate representative site conditions. If EO/IR is included, evaluate that channel separately rather than assuming every sensor retains the same performance in difficult weather.

14

How does acoustic detection cope with compressors, flare stacks and plant noise?

Compressors, flare activity and other plant noise can mask or complicate drone sound. New Ark's approach includes AI-assisted acoustic assessment, but that is not a guarantee that every industrial sound will be rejected or every drone separated from it. The site's normal and changing background activity matters.

Begin with a noise survey covering relevant operating conditions and possible array locations. During validation, label both drone observations and plant activity, measure false alarms over a defined period, and assess detection separately. Multi-sensor corroboration can help evaluate ambiguous acoustic observations.

15

What false alarm rate should we expect?

There is no verified universal false-alarm rate to apply to your site. A meaningful rate needs a defined observation period, operating conditions and a clear definition of a false alarm. Continuous plant activity, intermittent machinery and other sound sources should be represented in the evaluation.

Agree how alerts will be logged and checked against labelled ground truth, including periods without target drones. Report false alarms alongside detection probability and relevant conditions; simply reducing alerts is not evidence of better performance if genuine targets are also missed.

16

Can you detect and track a swarm?

Multi-object detection and persistent tracking are different requirements. New Ark's About page includes concurrent-object references for initial project discussion, but these are not guaranteed swarm performance or track-continuity results. Several simultaneous sound sources must be assessed for the selected configuration and the site's acoustic conditions.

Define the number and types of targets, their separation and the outputs you need. An authorised validation should measure detection, source separation and track continuity independently, with labelled observations. Radar or EO/IR corroboration can be included, without treating sensor information as authorisation for a response.

17

What range can you actually achieve against a DJI-class drone?

A DJI-specific detection range is not established here. The published multi-rotor range context is for initial project discussion, not a guaranteed result for a particular DJI model. Rotor sound, flight condition, industrial noise, wind, propagation and obstructions all affect the usable acoustic signal.

Specify the exact aircraft and configuration, the distances to evaluate, and whether success means an initial detection, classification or continuous track. Request an authorised field validation with labelled observations under representative conditions. A range figure without those conditions and endpoints is not a reliable procurement specification.

18

How precise is the location you report?

An acoustic array measures directional information; a bearing is not automatically a complete position or altitude estimate. Networked arrays may support angle-of-arrival bearing intersection when surveyed geometry and suitable observations are available. No universal localisation accuracy is established for a proposed installation.

Ask which outputs the selected configuration actually provides and how their uncertainty is represented. Validate position error separately from detection and tracking, using labelled target locations, agreed distance and environmental conditions, and defined measurement endpoints. Do not treat an azimuth specification as proof of three-dimensional location accuracy.

19

How much warning time do we get before a drone reaches the asset?

Warning time depends on where a usable detection first occurs, the aircraft's movement and the time required to deliver an alert. A catalogue range does not establish a guaranteed warning interval, especially where noise or obstructions delay the first reliable observation.

Define the protected asset boundary and measure the interval between an agreed alert endpoint and the target reaching that boundary during authorised validation. Assess detection and notification delays separately, and confirm how operators receive and interpret the alert. Detection information alone does not authorise an active countermeasure.

20

Does the system emit anything that could interfere with our radios or instrumentation?

Passive acoustic sensing measures existing sound rather than transmitting sensing RF. That describes the sensing principle, not an assurance that the complete installation has no electromagnetic emissions. Powered electronics and any networking equipment still require electromagnetic-compatibility and site review.

Assess the exact array, processing and communications configuration against your radios and instrumentation. Request the applicable conformity documents and have the responsible site specialists review installation compatibility. Passive sensing should not be interpreted as explosion-proof construction, exemption from every licence or a blanket guarantee of interference-free operation.

21—34

Products & Technical Specifications

Read topic
21

Which 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.

22

How 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.

23

What 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.

24

How 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.

25

What 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.

26

What 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.

27

What 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.

28

How 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.

29

What 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.

30

Does 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.

31

How 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.

32

Can 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.

33

How 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.

34

What 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.

35—43

Performance & Field Validation

Read topic
35

What detection probability can we expect at 500 m, 1 km and 2 km?

No verified detection probabilities at 500 m, 1 km or 2 km are established here. Published range context is not a probability curve and cannot show how often a defined target will be detected at each distance. Target characteristics and site conditions must accompany any such result.

Agree the aircraft, flight conditions, distances, observation counts and detection endpoint for an authorised test. Record labelled ground truth and background activity, then report detection probability separately at each agreed condition alongside false alarms. Do not extrapolate one successful observation into a reliable probability at longer distances.

36

How does range change with drone size and payload?

Acoustic detection depends on observable motor, rotor and airframe sound, not size alone. A larger aircraft or a different payload does not establish a predictable detection-distance increase. Flight condition and the sound's propagation through the site's noise, terrain and obstructions also affect the usable observation.

Compare the specific aircraft and payload configurations relevant to your project in an authorised evaluation. Keep the distances, environmental conditions and detection definition explicit, and report results for each tested configuration. Do not convert a fixed-wing or multi-rotor catalogue reference into a universal size-to-range rule.

37

Can you detect a 150 km/h FPV drone?

A verified capability against a 150 km/h FPV drone is not established here. Acoustic sensing may observe its motor and rotor sound, but aircraft speed alone does not determine whether a usable detection or continuous track will be obtained. Noise, propagation and observation conditions remain important.

Define the exact aircraft, evaluation conditions and required outputs for an authorised field test. Measure detection, time to alert and track continuity separately with labelled ground truth. A general drone-detection description should not be interpreted as a validated high-speed target specification or an interception capability.

38

What happens when several drones approach at once?

Simultaneous drones create a multi-source assessment problem: detecting several sounds is not the same as keeping a separate, continuous track for each aircraft. The selected system's behaviour needs validation, and published concurrent-object references do not guarantee results for every group or acoustic environment.

Specify the simultaneous target count, separation and required alert and track outputs. Assess labelled observations for missed detections, false alarms and continuity, and confirm how uncertainty is communicated to operators. Any response remains separate from detection and must be reviewed by the responsible legal and safety authorities.

39

Can you detect a drone that is gliding or hovering silently?

A powered hovering rotor is not silent, although its sound may be too weak or masked to provide a usable observation at the array. A quiet gliding aircraft can be an acoustic limitation because detection depends on sound that actually reaches the sensor.

Do not treat hovering and gliding as the same test condition. Evaluate the relevant aircraft states against site noise, distance and obstruction, with detection defined clearly. Complementary radar or EO/IR can be considered where acoustic evidence is limited, rather than claiming that acoustic sensing detects every apparently silent aircraft.

40

How do we validate performance before we buy?

Use an agreed, authorised field-validation plan tailored to your facility rather than relying only on catalogue descriptions. Start with a survey of noise, obstructions, permitted installation boundaries, access and available power and networking. Define the proposed configuration and the target aircraft before testing.

Agree distances, conditions, observation counts and measurement endpoints for detection probability, false alarms, localisation error, time to alert and track continuity. Record labelled ground truth and relevant background activity. Demonstration arrangements and acceptance criteria should be confirmed through the contact page; no trial duration or pricing is established here.

41

Do you have third-party or government laboratory test results?

No specific third-party or government laboratory report is verified here. Ask whether an applicable report can be shared for the exact product and version under consideration. A laboratory name alone would not establish that its tests cover your intended targets, environment or required outputs.

Review the test scope, methods, conditions, sample counts and measurement endpoints, and distinguish laboratory results from site performance. Where the available scope does not match your application, agree additional authorised field validation. Do not substitute a product video or an unspecified endorsement for the actual test documentation.

42

How much does weather degrade detection?

No verified percentage loss or universal weather-to-range adjustment is established here. Wind, rain and changing sound propagation can affect acoustic signal quality, while terrain and obstruction interact with those conditions. Their effects should not be reduced to one constant for every target and site.

Include representative weather conditions in an authorised evaluation and record them with each observation. Compare detection probability, false alarms and localisation or tracking outputs separately. Confirm hardware operating limits as well; surviving an environmental condition and maintaining the required detection performance are different acceptance questions.

43

How do you avoid mistaking birds or machinery for drones?

AI-assisted acoustic assessment can be part of evaluating sound sources, and multi-sensor corroboration can help assess uncertain observations. Neither establishes a guarantee that birds or machinery will never produce a false alert. Detection and classification should be evaluated as separate outputs.

Include normal machinery activity and observed bird activity in labelled validation data, alongside target-drone observations. Define what counts as a false alarm and measure it over an agreed period. Ask how confidence and uncertain classifications are presented to operators rather than assuming every alert confirms a drone's identity.

44—54

Deployment & Installation

Read topic
44

How do we plan array placement for a five-kilometre perimeter?

A five-kilometre perimeter does not translate into a fixed number of arrays or a universal spacing rule. Coverage depends on site geometry, noise, obstructions, permitted installation boundaries and the required outputs. Published range context should not be used as a guaranteed node-spacing specification.

Begin with a site survey and a proposed coverage assessment identifying access, power, networking and responsible parties. If localisation is required, review surveyed geometry for suitable AOA bearing intersection. Validate the proposed layout under representative conditions before committing to a final deployment scope.

45

What is the maximum cable run from an array to the control room?

The maximum run depends on the chosen power and communications design, not on acoustic sensing alone. No universal cable distance or supported transport arrangement is established here. The array's interface requirements and any intermediate equipment must be identified before infrastructure lengths can be assessed.

Provide the proposed route and site constraints, and request a configuration-specific infrastructure review by qualified personnel. Confirm the approved communications path, equipment responsibilities and acceptance tests in writing. Do not assume PoE, a particular cable type or an extension method is included without checking the selected configuration.

46

Can the arrays be installed in ATEX or IECEx zones?

ATEX or IECEx suitability is not verified here. Passive acoustic sensing does not mean explosion-proof construction, and an outdoor enclosure rating is not a hazardous-area approval. Installation must be assessed against the actual area's classification and the exact equipment configuration.

Request any applicable certificates and check their product version, scope, conditions, issuer and validity with competent site specialists. The site survey should establish permitted installation boundaries before a location is chosen. Do not assume an array can enter a hazardous zone without the required equipment and installation review.

47

Do we need concrete foundations?

Not every proposed installation can be assumed to require a new concrete foundation, but no universal foundation-free arrangement is established either. The need depends on the selected equipment, permitted location and support arrangement, all of which require site-specific review.

Provide the actual equipment dimensions and mass to qualified site personnel and confirm whether an existing structure or another approved location is suitable. Agree responsibilities for structural assessment, approvals and any civil works. Foundation type and sizing should come from the responsible project specialists, not a general product answer.

48

How long does installation and commissioning take?

A standard installation or commissioning duration is not established here. The schedule depends on the agreed equipment and integration scope, site access, permitted locations, available power and networking, and readiness of any required civil works. Commissioning also needs clearly defined acceptance activities.

Request a project schedule separating delivery, site preparation, installation, interface checks and authorised performance validation. Assign responsible parties and prerequisites for each stage, then confirm acceptance criteria and handover requirements in writing. A hardware installation estimate alone should not be treated as the complete operational-readiness date.

49

Who installs it: your team, a partner, or our contractor?

The installer and delivery responsibilities must be agreed for your project; a standard assignment to New Ark, a partner or your contractor is not established here. Local assembly, maintenance and spare-part arrangements can be discussed within written scope, but they do not automatically define installation services.

Specify who handles site preparation, mounting, infrastructure, system integration and commissioning, and who approves each stage. Confirm the qualifications and site permissions required for the work. A clear responsibility matrix helps avoid gaps between equipment delivery and an installation accepted by your facility.

50

How is the system calibrated, and does calibration drift?

The calibration method, allowable drift and recheck interval need confirmation for the selected array and installation. No universal drift figure or calibration schedule is established here. Directional observations and any AOA bearing-intersection arrangement also depend on correctly surveyed geometry and suitable observations.

Ask for the project's calibration and verification procedure, responsible parties and acceptance measures. Confirm how changes to equipment position or the installation will be reviewed, and how questionable directional or position outputs are checked. Maintenance and recalibration obligations should be documented rather than assuming lifelong stability.

51

What civil works and trenching are involved?

Civil works and trenching depend on the approved locations and the chosen power and network infrastructure. They are not fixed requirements of acoustic detection, and a universal excavation scope is not established here. Existing site infrastructure must be reviewed before assuming either new works or no works.

Use the site survey to document installation boundaries, access, available services and responsible parties. Request a project-specific civil and infrastructure scope with approvals and acceptance responsibilities clearly assigned. Qualified site specialists should determine routes and structural requirements; a product description should not be used as a construction design.

52

Can it run on solar or battery power at remote sites?

Solar or battery operation needs a configuration-specific feasibility review; support for either is not established as a standard option here. The assessment must include the array and all associated processing and communications equipment, rather than considering only the sensor's power needs.

Confirm actual power requirements, intended operating periods, environmental conditions and permitted network arrangements with qualified project personnel. Define responsibilities for the complete remote-power solution and its acceptance. Do not assume a particular battery runtime, solar size or uninterrupted operation without a documented design and validation for the selected system.

53

How do you protect the arrays from lightning, corrosion and vandalism?

Protection against lightning, corrosion and vandalism needs a site-specific equipment and installation review. No universal protection package or resistance rating is established here. Environmental exposure, permitted mounting locations, access and the chosen enclosure should be assessed together rather than assuming outdoor use covers every hazard.

Ask qualified site specialists to review the applicable protection requirements and request evidence for the exact delivered configuration. Agree responsibilities for installation protection, inspection and maintenance in the project scope. Keep equipment survivability distinct from guaranteed detection performance, and avoid treating a generic enclosure claim as a complete site-protection design.

54

Can we start with a pilot and expand later?

A staged pilot and expansion plan can be discussed, but expansion compatibility and commercial arrangements must be confirmed for the chosen configuration. A pilot should test the site's acoustic conditions and required outputs, not be treated as proof that the same layout scales to every additional area.

Agree the pilot boundaries, targets, acceptance measures and data responsibilities before deployment. For later phases, confirm hardware and software compatibility, interfaces, surveyed geometry, infrastructure and support scope. Each expanded area should have its coverage and integration assessed rather than assuming the pilot's results guarantee wider performance.

55—63

System Integration & C2

Read topic
55

Can New Ark integrate with our existing VMS or PSIM?

Integration can be discussed, but compatibility with your particular VMS or PSIM must be confirmed. New Ark's published approach includes C2 integration, and its PCBA delivery scope supports discussion of SDK/API and integration interfaces. This does not establish an available plugin for any named platform.

Provide the platform name, version and required workflow. The written interface scope should define alert fields, coordinates, timestamps, confidence information, authentication, versioning and responsibilities, with acceptance tests demonstrating that your control room receives and interprets the information correctly.

56

Can it cue our PTZ cameras automatically?

Automatic camera cueing should be treated as an integration requirement, not an assumed capability of every configuration. New Ark lists an acoustic and EO system reference, but an acoustic bearing is not necessarily a validated target position or altitude that your camera can directly use.

Confirm the camera model, control interface, surveyed sensor geometry and coordinate conventions. Agree how confidence, unavailable position information and camera confirmation are handled, then test the complete cueing workflow at your site before accepting automatic operation.

57

Can you fuse acoustic tracks with radar, RF and EO/IR?

Multi-sensor corroboration is part of New Ark's published approach, and the catalogue includes fusion, radar/RF and optical/thermal references. These references do not guarantee that every third-party sensor or track format can be fused without configuration and validation.

Define each sensor's outputs, coordinate and time conventions, confidence fields and responsibility for track association in the integration scope. Acceptance tests should distinguish detection, classification, position and persistent track continuity, including cases where sensors disagree or one source becomes unavailable.

58

Do you support ONVIF, Modbus or OPC-UA?

Support for ONVIF, Modbus or OPC-UA has not been established for the available configurations. Treat these as requested interfaces to check, rather than published compatibility claims. New Ark's PCBA delivery scope allows discussion of integration interfaces, but the exact protocol implementation requires project confirmation.

Specify the protocol version, required messages, read or control functions, authentication and receiving equipment. The written scope should identify any development or gateway responsibility, licensing and acceptance tests, including how errors and unavailable sensor information are represented.

59

Is there an API or SDK, and what does it cost?

API and SDK arrangements can be discussed within New Ark's PCBA delivery and integration scope. Their availability, contents and cost depend on the selected configuration; a public interface price or automatic inclusion with hardware is not established.

Ask the quotation to identify the functions and data fields provided, documentation, access rights, licensing, version compatibility and integration responsibilities. Separate any development, testing and support charges from hardware pricing, and confirm whether future interface changes or updates are covered by the agreement.

60

How do alerts reach our control room or phone?

Alert delivery needs to be specified for your control-room workflow and network environment. New Ark's published direction includes C2 integration, but no particular phone application, messaging service or notification channel should be assumed to be included.

Describe who must receive an alert, which information they need and how acknowledgement should work. Confirm the receiving interface, connectivity, authentication and responsibilities in writing. Acceptance testing should cover normal delivery, duplicate alerts and connection loss, with clear measurement endpoints rather than an unqualified notification-time promise.

61

Does it work on-premise, offline, or in the cloud?

New Ark describes an edge-processing direction, but this does not establish a default on-premise, offline or cloud deployment. The architecture must be confirmed for the chosen configuration, including which functions depend on a server, network connection or external service.

Specify the functions required during disconnection and where raw audio, features and events may be processed or stored. The project scope should document connectivity dependencies, access, transfers and recovery behaviour, then verify the required operating mode through acceptance tests rather than assuming complete offline capability.

62

Can the system use drone Remote ID?

Remote ID integration is a requirement to verify, not an established feature of the selected system. Passive acoustic sensing observes sound; it does not read broadcast identifiers or establish a drone's identity simply from hearing its motors or rotors.

If your project requires Remote ID information, identify the proposed authorised reception source and the fields needed by the control platform. Confirm interfaces, time and coordinate conventions, confidence handling and applicable local requirements, then test how that information is corroborated with acoustic observations.

63

Can the platform control third-party effectors?

Third-party effector control must not be assumed from C2 integration or the catalogue's high-level authorised-response references. Compatibility, contractual scope and lawful authority are separate questions, and sensor information alone does not authorise action.

Keep detection integration distinct from any active-response proposal. Competent legal and safety authorities, together with accountable qualified personnel, must assess whether the proposed response is permissible. Any approved project scope should clearly separate information exchange, system responsibilities and authorisation responsibilities, without treating an acoustic alert as permission to engage.

64—72

Operations & Legal Responsibilities

Read topic
64

Does New Ark supply jammers, and are they legal in our country?

The catalogue's high-level authorised-response references do not establish that a particular jammer is supplied or lawful in your country. New Ark's RF power-amplifier modules are described for lawful communications, testing and research; that description is not a claim of jammer availability or permission to interfere with radio signals.

Separate detection-only requirements from any active countermeasure request. Confirm the exact configuration, destination, end user and intended use, and obtain assessment from competent legal, radio and safety authorities before considering procurement or operation.

65

How does the FPV interceptor work, and who authorizes a launch?

An FPV interceptor is an active-response concept, separate from acoustic detection. The catalogue's high-level authorised-response references do not establish a particular interceptor's operating method, performance or launch process. An acoustic alert is sensor information, not launch authority.

Who may authorise deployment depends on the jurisdiction, site and approved operational scope. Competent legal and safety authorities and accountable qualified personnel must determine the permissions and responsibilities. These must be documented before any active-response procurement; detection-only evaluation can be scoped separately without assuming an interceptor is included.

66

What is the cost per interception?

A verified cost per interception is not available, and a detection-system quotation should not be interpreted as an interception price. Any active-response budget first requires a lawful, approved scope assessed by competent authorities and qualified personnel.

For commercial comparison, distinguish equipment and integration costs from installation, commissioning, training, spares and support. Define what the proposed cost measure includes and whether it refers to an attempted action or a confirmed outcome. Ask for written project-specific assumptions rather than treating a headline amount as a guaranteed cost or result.

67

What if the interceptor misses or hits the wrong object?

A missed interception or action against the wrong object is a safety-critical failure scenario, not something an acoustic detection claim can resolve. No miss probability, interceptor outcome or liability allocation should be assumed from the published catalogue references.

Before considering active response, competent legal and safety authorities and accountable qualified personnel must assess the consequences for the specific site. The approved scope should address responsibilities and incident reporting. Detection and corroboration can inform assessment, but neither an alert nor a classification guarantees correct identification or a safe response.

68

Can we run detect-only with no countermeasure?

Detection-only planning is separate from active countermeasures, so your project can be framed around sensing, assessment and alert integration without requesting an active-response scope. Confirm the selected hardware and software configuration rather than assuming that every catalogue reference is included.

Define the outputs operators need, how alerts are corroborated and who receives them. The agreement should identify installation, data handling and acceptance requirements. Sensor information does not authorise action, and any later proposal for active response would require a separate assessment by competent legal and safety authorities.

69

How do you prevent engagement of aircraft or birds?

No acoustic classification should be treated as a guarantee that an object is safe to engage. Detection, classification and identification are distinct, and New Ark's published multi-sensor corroboration direction does not establish perfect discrimination between drones, aircraft and birds.

Validate classification and false alarms using labelled observations and relevant background activity. Keep sensor assessment separate from action authorisation. Any active-response proposal must be evaluated by competent legal and safety authorities and accountable qualified personnel; the written scope should establish responsibilities without making an alert an automatic permission to act.

70

What is the end-to-end response time?

There is no single verified end-to-end response time. Sound observation, detection, alert delivery, corroboration and human assessment have different measurement endpoints; an active response also requires lawful authorisation and must not be inferred from detection latency.

For a detection-only project, define the starting event and control-room endpoint, then measure time to alert under agreed targets, distances and conditions. If active response is contemplated, competent legal and safety authorities and qualified personnel must assess that separate scope. Avoid combining unrelated timings into an unsupported overall performance promise.

71

Who is liable if a drone is brought down over a populated area?

Liability cannot be assigned from a product description or sensor alert. It depends on the jurisdiction, authorised activity, parties' responsibilities and circumstances of the incident. New Ark's published response references do not establish a liability or insurance arrangement.

Before procuring active countermeasures, obtain assessment from competent legal and safety authorities and accountable qualified personnel for the intended site. Document the approved scope and contractual responsibilities without treating the contract as a substitute for legal review. A detection-only project should remain clearly separate from any authority to bring down a drone.

72

Can a small security team operate it?

Team size alone does not determine operational suitability. For detection-only use, assess the number of monitored areas, expected alert workload, control-room workflow and staff availability. No verified minimum staffing level or operator qualification package is established.

The project scope should define operator duties, training, alert interpretation, reporting and maintenance responsibilities, then validate the workflow with the intended users. Active countermeasures require a separate review by competent authorities and accountable qualified personnel; the ability to monitor detections does not establish qualification or authority to conduct an active response.

73—86

Pricing, Procurement & OEM

Read topic
73

What does a basic system cost?

There is no verified standard price for a basic system. The useful starting point is your detection objective and site conditions, not a presumed package. Hardware selection, software scope and integration requirements determine what needs to be quoted.

Provide the area to monitor, background noise, available power and network, and required control-room outputs. Ask for an itemised quotation separating equipment from installation, commissioning, training, spares and support. Confirm what is included and excluded so that a lower initial equipment price is not mistaken for a lower complete project cost.

74

How do you price a project?

Project pricing should follow an agreed technical and delivery scope. Relevant cost categories include selected hardware, software, integration, installation, commissioning, training, spares and support; no standard pricing formula or commercial terms are established.

Define site boundaries, required sensor outputs, interfaces, acceptance tests and each party's responsibilities before requesting a quotation. Ask that optional items, assumptions and exclusions be listed separately. This makes proposals comparable and clarifies which scope changes would require a revised price, rather than relying on an undefined price per array or per kilometre.

75

What is the five-year cost of ownership?

A five-year ownership estimate needs a defined configuration and lifecycle assumptions, so a single total cannot be established without a project scope. Include hardware and software alongside integration, installation, commissioning, training, spares and support rather than considering the purchase price alone.

Ask the written proposal to distinguish upfront charges from recurring or conditional costs. Confirm warranty scope, repair arrangements, maintenance intervals and software update entitlement, since none should be assumed to cover the full five years. Compare estimates using the same site requirements, operating period and exclusions, with uncertainties shown explicitly.

76

Do you offer leasing, rental or detection-as-a-service?

Leasing, rental and detection-as-a-service availability must be confirmed for your project. These are not established standard offerings, and equipment availability does not imply an operating service or a particular financing arrangement.

Describe the deployment period, site, required outputs and who would operate the system. If an alternative commercial model is proposed, confirm equipment ownership, installation, data responsibilities, maintenance, support and end-of-term arrangements in writing. Compare the complete scope and cost with a purchase proposal, rather than assuming rental includes staffing, integration or guaranteed detection outcomes.

77

What is the lead time from purchase order to delivery?

Delivery lead time is project-specific; no standard interval from purchase order to delivery is established. The selected configuration, quantities, integration work and destination requirements all need to be resolved before a meaningful schedule can be agreed.

Ask the quotation to define the delivery milestone and its starting conditions, including technical approval and agreed commercial requirements. Distinguish equipment dispatch and arrival from installation, commissioning and acceptance. Record responsibilities, dependencies and the process for communicating schedule changes in writing, rather than treating an indicative date as a complete operational-readiness commitment.

78

What are your payment terms and Incoterms?

Payment terms and Incoterms must be agreed in the project quotation and contract; no standard deposit, credit period or delivery rule is established. The relevant terms depend on the parties, configuration and destination.

Request written confirmation of the payment schedule, currency and milestone definitions. For Incoterms, identify the agreed rule, edition and named place, and clarify responsibility for transport, customs, taxes and related costs. Keep commercial delivery obligations separate from installation and acceptance requirements so that each party understands what a payment or delivery milestone actually covers.

79

Is there a minimum order quantity?

Minimum order quantity must be confirmed for the selected product and delivery scope. There is no established universal minimum for arrays, PCBA deliveries or customised configurations, and a small pilot request should not be taken as proof that any quantity is available.

Specify the model, initial quantity, anticipated expansion and required customisation when asking for a quotation. Confirm whether quantity affects development charges, unit pricing, testing, spare-part arrangements or delivery scheduling. Record the agreed minimum and any separate conditions for later repeat orders in the written commercial scope.

80

Do you offer distributor or integrator margins?

Distributor and integrator commercial arrangements are project-specific; no standard margin, discount or territory entitlement is established. A proposed partnership should define what each party contributes rather than assuming a published reseller programme.

Describe your market, technical responsibilities, expected quantities and support capabilities. Any written agreement should clarify pricing, territory, customer ownership, integration work, training and after-sales responsibilities, with exclusivity confirmed only if expressly agreed. Keep partner remuneration separate from the end customer's equipment and service scope so that obligations and costs remain understandable.

81

Can we buy the PCBA and build our own product?

New Ark's PCBA delivery scope supports discussion of microphone-array acquisition, acoustic processing and OEM/ODM projects. Buying a PCBA, however, does not automatically establish a complete product design, software licence or right to reproduce the technology.

Define your intended product and confirm board configuration, interfaces, BOM scope, production and testing responsibilities, quantities and commercial terms. The agreement should separately address SDK/API access, licensing and ownership, plus integration and acceptance requirements. Local assembly and spare-part arrangements can also be discussed within the written project scope.

82

Can you white-label the system under our brand?

Branding requirements can be raised within an OEM/ODM discussion, but white-label availability and rights require written confirmation. New Ark's PCBA delivery scope does not by itself establish permission to rebrand every system or claim ownership of its underlying hardware and software.

Specify the proposed product, brand presentation and intended markets. Agree the scope of hardware, software and documentation changes, licensing, ownership, testing and after-sales responsibilities. Confirm how product identification and applicable compliance documentation will remain accurate, rather than assuming a new label carries over every declaration or authorisation.

83

Can you customize detection for our specific drones or environment?

Your target drones and environment can inform a project-specific acoustic-processing discussion, but custom detection performance is not established in advance. Motor, rotor and airframe sound may be observable, while industrial noise, weather and obstructions can affect the usable signal.

Provide target types, operating conditions and representative background activity. Define the development scope, data permissions, deliverables and acceptance criteria in writing. Validation should use labelled ground truth and agreed observations to measure detection, false alarms and any required classification, without promising universal recognition or guaranteed range for your drones.

84

Do you provide demo units or a loaner kit?

New Ark's contact page accepts authorised demonstration and field-validation requests. This does not establish that demo units or loaner kits are available, or that a demonstration is free, paid or offered for a fixed duration.

Explain the site, target scenarios and decision you need the demonstration to support. Ask for written confirmation of equipment, availability, location, responsibilities, costs and return conditions if a loan is proposed. Agree observation conditions and measurement criteria beforehand so that the exercise evaluates your requirements rather than implying guaranteed coverage from a demonstration alone.

85

What currency and tax terms apply?

Quotation currency and tax treatment must be confirmed for the transaction; no standard currency, tax-inclusive price or exemption is established. The relevant details depend on the contracting parties, destination and agreed delivery arrangements.

Ask the quotation to state the currency, price validity and which taxes, duties or other charges are included or excluded. Clarify who handles customs and related payments, and seek appropriate local tax or customs advice where needed. Compare offers on the same delivered-cost basis instead of assuming the quoted equipment amount is the final payable total.

86

Can you hold stock or spare arrays for us?

Spare-part and local maintenance arrangements can be discussed within the written project scope, but reserved stock or spare-array availability is not a standard commitment. A spare strategy should reflect the selected configuration and the site's operational needs.

Specify which items you want held, quantities, storage location and ownership. Confirm reservation duration, replenishment, configuration compatibility, any charges and the conditions for releasing stock. Distinguish having a spare available from delivery, installation and restoration commitments, since none automatically establishes a repair turnaround or service SLA.

87—94

Compliance & Data Governance

Read topic
87

Is the equipment CE, FCC or RoHS certified?

CE, FCC or RoHS status must be confirmed for your selected configuration. Do not infer compliance from passive sensing, a catalogue listing or another product's documentation. The applicable evidence must match the equipment and configuration you intend to purchase.

Request any relevant certificate, declaration or test documentation, and check its product version, standards, scope, issuer and validity. Confirm with your procurement and competent compliance advisers which evidence is required for the destination and intended use. A document for one component should not automatically be treated as covering the complete installed system.

88

Are you subject to export controls, and can you ship to our country?

Export requirements and shipment availability must be assessed for the exact configuration, end user, destination and intended use. Neither an acoustic product listing nor a passive sensing description establishes unrestricted export availability or permission to import and operate the complete system.

Provide these project details before requesting a delivery commitment. Ask which origin, export and destination documentation can be confirmed for the proposed equipment, and have competent trade and local authorities review applicable requirements. Keep detection-only equipment distinct from any active-response proposal, which requires separate legal and safety assessment.

89

Are your products NDAA Section 889 compliant?

NDAA Section 889 compliance has not been verified for the proposed products. A brand name, assembly arrangement or passive sensing method does not establish eligibility for a particular procurement requirement.

Have your procurement and legal advisers identify the requirement applicable to your purchase. Request configuration-specific information and any relevant declarations, checking the product version and documented scope rather than accepting a broad marketing label. The written project scope should identify what evidence is required and who evaluates it; do not assume that a statement about one component covers the entire system or supplier relationship.

90

What is the country of origin of the hardware?

Hardware origin must be confirmed for the selected configuration. New Ark's legal name is Hong Kong New Ark Intelligent Technology Limited, but the company's name or local assembly discussions do not establish the country of origin of every board, array or completed system.

Specify whether your procurement needs component origin, assembly information or an origin document for the delivered product. Request configuration-specific evidence and have competent procurement or customs advisers assess its relevance. Keep BOM, assembly and finished-product origin questions distinct, particularly for customised PCBA or multi-sensor deliveries.

91

Do you hold ISO 27001 or any cybersecurity certification?

ISO 27001 or other cybersecurity certification has not been verified. A description of edge processing or C2 integration does not establish a certified security programme, and company-level and product-level assurance should not be treated as interchangeable.

If certification is a procurement requirement, request the applicable evidence and check scope, covered entity or product, standards, issuer and validity. Separately define project security requirements for interfaces, authentication, access, data locations and updates. Confirm which supporting documents can be provided, rather than assuming certification or the availability of security reports.

92

Does the system record voices, and is that lawful under GDPR?

Passive acoustic sensing does not automatically mean that voices are never recorded. The selected configuration's collection and storage behaviour must be confirmed, including whether it handles raw audio, derived features, events or identifiers. GDPR compliance cannot be inferred from the sensing method.

Document storage locations, retention, access, transfers and deletion, then obtain appropriate privacy and legal review for the site and intended use. Ask which supporting information can be provided without assuming a DPA, DPIA or security report is available. Any data-handling commitments need to be explicit in the project agreement.

93

Do we need a radio licence to operate?

Passive acoustic sensing measures existing sound rather than transmitting sensing RF. That distinction does not establish a blanket exemption from radio licensing or other local requirements: powered electronics, networking and any additional sensors still need site and regulatory review.

Identify the complete configuration, destination and intended use, including any wireless connectivity or RF equipment. Ask competent local radio and safety authorities to determine the applicable permissions and documentation. Detection-only planning should remain separate from active countermeasures, whose lawful operation cannot be inferred from permission to install an acoustic sensor.

94

Can you supply tender documents and compliance statements?

Tender documentation should be agreed against your procurement requirements and the proposed configuration. The availability of particular compliance statements, certificates or test reports is not established, so a catalogue description should not be substituted for required evidence.

Provide a document checklist covering technical scope, interfaces, acceptance criteria, origin and applicable standards. Ask which items can be supplied and identify unresolved requirements before submission. Check each declaration's product version, scope, issuer and validity, and clearly distinguish documented specifications, proposed project commitments and performance that still requires field validation.

95—100

Support & Product Lifecycle

Read topic
95

What warranty do you offer?

Warranty duration and coverage must be stated in the project agreement; no standard warranty length is established. Confirm the terms for the exact hardware and software configuration rather than assuming one policy covers every delivered item.

Ask when coverage begins, what defects are covered, which exclusions apply and how a claim is assessed. Clarify repair or replacement responsibilities, shipping costs and any site work. Keep warranty separate from spare availability, maintenance, software updates and support response commitments, since a warranty does not automatically establish an uptime guarantee or repair SLA.

96

What is the spare-parts and repair turnaround?

Spare-part availability and repair turnaround require project-specific confirmation. New Ark's published scope allows discussion of local maintenance and spare arrangements, but it does not establish stock levels, delivery dates or a guaranteed restoration time.

Identify critical items for the selected configuration and agree the reporting, diagnosis, return and repair responsibilities. Ask whether any proposed times refer to acknowledgement, assessment, dispatch or completed repair. Confirm shipping, customs, replacement compatibility and costs in writing; a spare arriving at the site is not necessarily the same milestone as restoring the system to service.

97

What training do you provide?

Training content, duration and delivery arrangements need to be agreed for the project; no standard course package is established. For detection-only use, useful requirements include interpreting alerts and confidence information, understanding limitations, reporting events and recognising when maintenance review is needed.

Specify the operator and technical roles, language, location and assessment criteria in the written scope. Confirm which materials and practical exercises are included. Any active-response training or qualification must be assessed separately by competent authorities and accountable qualified personnel; detection training does not itself confer permission to use countermeasures.

98

How much maintenance does the system need?

Maintenance workload depends on the selected configuration, installation environment and agreed operating scope. No fixed maintenance interval or maintenance-free claim is established. Noise conditions, obstruction and changes to the site can also affect whether performance needs to be reassessed.

Ask for a written maintenance plan identifying inspection items, authorised procedures, responsible parties and criteria for further testing. Clarify spare requirements, access arrangements and how sensor or network faults are reported. Keep routine maintenance separate from repairs and software updates, with their respective costs and entitlements confirmed in the agreement.

99

Are software updates included?

Software updates and patch entitlement must be confirmed in the project agreement; they should not be assumed to be included indefinitely with hardware. Security patches, feature changes and interface revisions may involve different scope and compatibility considerations.

Ask which update categories are covered, for how long, and who is responsible for deployment and testing. Confirm licensing, supported configurations, integration impact and any charges. The written scope should also address how changes are communicated and validated, without assuming a fixed release schedule, automatic updates or continued support for every previous version.

100

What is your support SLA, and is local support available?

Support SLA and local availability must be agreed for the project. New Ark's published scope permits discussion of local assembly, maintenance and spare arrangements, but it does not establish a local support location, service hours or guaranteed response and resolution times.

Specify the site, required coverage hours and fault priorities. The agreement should distinguish acknowledgement, technical response, on-site attendance and restoration, and name each responsible party. Confirm escalation channels, remote access conditions, spares and charges so that a general contact route is not mistaken for a contractual service commitment.

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.

Discuss your project