BUYER KNOWLEDGE / NEW ARK
System Integration & C2
Define sensor interfaces, multi-source information exchange, C2 integration, and accountable system-integration boundaries.
55—63
System Integration & C2
55Can 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.
56Can 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.
57Can 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.
58Do 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.
59Is 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.
60How 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.
61Does 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.
62Can 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.
63Can 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.
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.