Drone detection for infrastructure

At an event you know when the risk is there: three days, from gates open to gates shut. At a substation, a solar park, a water treatment plant or a chemical site it is different. There the risk is low and constant, and that calls for a different setup.

Why people fly above your site

• Reconnaissance ahead of theft. Cable, copper and inverters are worth money, and a drone flight shows where they sit and how the fence runs.
• Inspection by third parties without your knowledge, by an insurer, an agent or a journalist.
• Curiosity. A large solar park or a cooling tower makes an attractive image, and most flights stop there.
• For a small share: focused interest in the layout of a site designated as vital.

All four share the same problem: without a record you do not know whether the pattern is growing, and a pattern is the first thing a security department wants to see.

Permanent is a different product from temporary

A unit that stands on a tripod for three days is allowed to be awkward. A unit that hangs on a mast for five years has to survive that without anyone climbing up to it. So the DRID sits in an IP67 enclosure with a single PoE cable carrying both power and data. More in the specifications.

• No batteries to replace.
• One cable, so one penetration through the façade or the mast.
• Where there is no wired network, the optional 4G module takes over.
• Range 7.5 km in built-up areas and 15 km in open terrain, measured from an elevated position with line of sight. The measurement conditions are published with it.

The question vital sectors ask first

Where does the data sit, and who can switch the system off? At a festival that is rarely a discussion. At a grid operator, a defence site or a correctional facility it is a precondition.

So the DRID also runs entirely offline on a server inside your own network. No outbound connection, no licence key that expires, and no way for us to stop your installation remotely. Read exactly what we mean by that under deployment models.

What you build up

With a permanent installation the value is rarely the single incident. It is the history. After six months you see which days and times recur, whether the same serial numbers come back and whether the count is rising. That is the substantiation a security department needs to propose a measure that costs money.

• Every observation with time, serial number, altitude and the pilot’s position.
• Zones with their own threshold, low above the installation and higher above the car park for instance.
• Alerts by SMS to whoever is on duty, or through the API into your own control room software.
• Export to CSV or JSON for your own analysis.

Connecting to what you already run

Detection is rarely the end point. The observations have to reach the system your control room already uses. For that there is an open REST and JSON API, and the interface additionally follows the SAPIENT standard for sensor integration in counter-UAS architectures. Details under integration.

Want to know how many units your site needs? Send us a site plan and we will give a substantiated figure instead of a standard number. Request a quote.