The four RAVEN C2 working views: optimisation, debrief, analytics and heatmap
RAVEN C2 · command and control

Every sensor on one screen.

Radars, cameras and radio sensors across a site report into one map, so the operator sees one track per aircraft instead of four. Nothing is acted on without a person deciding.

One picture. One policy. One authorised action.

RAVEN C2 fuses every connected sensor into a single operating picture, classifies what it sees, presents the operator with the lawful response options for that site, and records the whole chain for review.

Sensors and response options attach as modules. The operational core stays the same as the deployment grows, from one protected site to a national network.

3–5 s Takeover time per aircraft
~3 m Landing radius, GPS-defined point
< 1 day Operator training
How an engagement runs
  1. 01Detect Connected sensors report the aircraft and a track opens, with real-time alerting.
  2. 02Understand Identity, location, track and supporting evidence consolidated into one operational picture.
  3. 03Decide The site's policy, the threat classification and the operator's authority determine the response. A named operator confirms or holds.
  4. 04Respond Where lawfully authorised, control of the aircraft is taken and it is guided to a designated landing zone, or disconnected.
  5. 05Assess Alerts, tracks, system actions and operator decisions are retained for reporting and post-event review.
Four working views
RAVEN C2 optimisation view
01

Optimisation

Model coverage before deployment. Sensor siting, terrain and overlap are evaluated against the protected area, then replanned as the site or the threat axis changes.

RAVEN C2 debrief view
02

Debrief

Replay any event with the full track, the identity data and the operator actions taken, on the timeline they happened.

RAVEN C2 analytics view
03

Analytics

Activity volume, distinct airframes, mitigation counts and the most-encountered models over time — the evidence base for posture decisions.

RAVEN C2 heatmap view
04

Heatmap

Where incursions concentrate, by appearance and duration, so sensors and patrols are positioned against real patterns rather than assumptions.

Screens shown with demonstration data

Open by design

RAVEN C2 sits in the mission layer. Sensors report into it, and it reports on into the command system the customer already runs.

Detect · identify

Sensors

Radio-frequency detection, with radar, electro-optics and Remote ID as options

Mission layer

RAVEN C2

Sensor fusion · policy workflows · response orchestration · event recording

Command

Customer C2 / C4I

The end user's existing command systems

Respond

Controlled mitigation

Protocol takeover and a controlled landing

Two-way integration through a REST API or WebSocket. Each sensor or system interface is assessed and scoped individually.

Additional sites and stakeholders join the same operational core rather than replacing it.

What it gives you

Identity, not a dot on a map

Vendor, model and serial number where the aircraft carries one. Authorised aircraft on the allow-list are neither tracked nor engaged.

The picture keeps running

Detection and tracking of other aircraft continues while a mitigation is in progress.

One picture across sites

Events, policies and workflows from every connected node, consolidated in one place.

Everything is on the record

The track, the evidence, the proposal, the decision and the operator are written down as the engagement runs.

Full specification

The datasheet is issued under a non-disclosure agreement, against a named programme.

Request the datasheet
  • Monitored bands and transmit power
  • Power and environmental envelope
  • Deployment kits
  • Integration and interface scoping
  • Delivery, warranty and support
  • Lead time and export licensing